It makes sense to me. Besides the CL cache, the Java ClassLoader that ultimately loads the class will cache it as well; the same classloader will only load the bytes for a particular class once so there shouldn't be the need to cache class resources outside that...