JIRA issue: http://jira.jboss.com/jira/browse/JBMICROCONT-234 I'll apply the "hack" to fix the problem. The test will pass when the latest MC stuff is applied to JBossAS trunk. I don't know what to do about the Class.forName() caching? Maybe we could add a System.gc() - even though it is only a hint - whenever somebody undeploys something to try to speed the cleanup of the JDK internal cache. Or maybe there is a JDK specific api we could call from undeploy to flush the cache? i.e. users could configure the call if they are experiencing the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126764#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...