Due to the way the JDK creates temporary constructors, and the way the weak references work in the JDK, the weak reference cache will almost always leak constructors over time when, for example, multiple EJB requests are performed to a WildFly server. To solve the issue, the weak ref cache has been eliminated and replaced with a strong reference cache which provides an API to drop a class loader's cache on undeploy.