"flavia.rainone(a)jboss.com" wrote : | On our side of the story, the ClassLoader is registered on an as-needed basis, by RepositoryClassPoolFactory.getPoolForLoader(ClassLoader). I dunno it would be a good idea to create a translator just for the sake of unregistering classloaders. What would be a better approach? Maybe a LifecycleCallback? Uf, translator idea is horrible. ;-) We are already able to track when the ClassLoader goes away: when the Module is discarded --> ClassLoading::removeModule. And this is what I already fixed, so that the RegisterModuleCallback is part of this ClassLoading::removeModule call. It just looks like this doesn't do all the things we need to properly cleanup ClassPools. Or perhaps we already cleanup - as that null would indicate, it's just that we don't properly re-set things; e.g. in 2nd call to the TypeInfo/ClassPool getClassLoader. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260720#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...