Performance tests of remote lookups of EJBs are lagging.
One key contributor to this is the excessive time spent in looking up classes in the class loader; the JDKBridge class pends a lot of time loading classes (which is in turn quite expensive because the lower classes throw a lot of ClassNotFoundExceptions along the way). We need to cache the classes better to avoid these lookups.
In fact, I see that in the JDKBridge class there already is a class cache, but it has been disabled because it doesn't work correctly between applications. We must fix that; when I enabled it for our throughput test of EJB lookups, performance improved by 25%.