In class BlossomModuleSupport, when calling method closeRootWebApplicationContext(), the spring application context is closed correctly, but the "contextLoader" in the class is not set to null.
When a blossom module reloads itself (which may happen on any change on /modules/<module>/config node), the spring application context can be closed, but a reference to the contextLoader is left anyway. When the start of the module is called, it finds an instance of contextLoader (even if the context is closed) and throws exception, so it's impossible to reload context until server restart. Is this wanted for some reason or it is a bug?
If it is wanted you should update the example on the wiki page to avoid spring re-initialization when the lifecicle of the module is a simple reload and not a system start/shutdown (which I think it would be a good practice anyway).