I think the key is to get away for the pure static ClassLoaderHelper. Given that your service architecture is now very similar to the ORM one , we maybe can do something based on the ORM ClassLoaderService. I'll have a look.

Other than that I agree with Emmanuel Bernard, that one additional app class loader seems sufficient for now. I don't see a use case for granular class loaders as suggested.