service apparmor does not unload profiles that have been disabled

[Max Timchenko]

After creating a symlink in /etc/apparmor.d/disable and running 'service apparmor reload', I would expect that the affected profile would be removed from the kernel. Instead, the service simply skips over the profile definition and the profile remains active.

Creating a symlink in 'force-complain' does work as I expect - reloading the service moves the profile to complain mode. Removing the symlink returns the profile to enforce mode.

This is an inconsistent behavior. I could make a stab at a patch but want to confirm first this is not a deliberately designed (if, in my opinion, misguided) feature of AppArmor utilities.