In addition to the memory leaks occurring on application redeployment (see
#12368), Weld requires excessive amounts of memory even for a moderately sized
My WAR (using Wicket+EJB+JPA) running on Glassfish 3.1-b26 requires about 400 MB
heap memory. The Eclipse Memory Analyzer reveals that almost 200 MB are occupied
by instances of org.jboss.weld.introspector.weld.jlr.WeldClassImpl.
Downgrading my application to Java EE 5 style injections with @EJB instead of
@Inject, I could cut the memory usage of my application by 50 %.
Other projects may have different priorities, but for me, this is a severe
quality issue which made me stop using CDI altogether, until this issue is solved.