The ServletDispatchingFilter calls the init() method of the wrapped servlet on start-up.

When the contents of the servlets tree in /server/filters/servlets are changed in the magnolia admincentral, magnolia reloads the filter chain
to enable the changes to be processed, and thus creates a new instance, and calls the init() method.
The destroy method of the wrapped servlet does not seem to be called.

In my opinion it would be nice to also dispatch the destroy method to the wrapped servlet. At the moment the destroy() is completely ignored
by the ServletDispatchingFilter. This might lead to unexpected behaviour in some scenarios.