The simple contract for plugins is that the Jenkins singleton should always be available on the master on any execution path that is available to code in a plugin's classloader.

Arguably this is not needed as the plugins should be removing their filters, but where filters are registered via the @Extension mechanism this could not be guaranteed