I get frequently the following error in Eclipse 3.2 (Callisto) :"Exception in thread "Java indexing" java.lang.OutOfMemoryError: Java heap space". I didn't noticed this problem before 3.2, so I assume it is a newer bug. I even set the heap already to 600 mb (-Xmx600m), without improvement.I work with some EMF-projects (also with generated code with EMF.codegen), but they are not very large. It is not big problem, but I've to restart Eclipse now frequently... 

I attended a session at a small conference in the north of germany, about a bigger enterprise project and was afterwards a little bit confused. The speaker mentioned several times: "J2EE was unusable, so we had to use JMS" or "We evaluated J2EE, but we choose JMS instead (Java Messaging Service)". After the session I tried to persuade the speaker, that JMS is an important part of J2EE, but I think he didn't believed me.

Also in projects I've often to struggle with this opinion. At the beginning of a project I clearify, that EJBs are only a small part of the Java EE 5 specification. Developers tend to associate J2EE / Java EE 5 with EJB, so this fact can often lead to intense discussions. I think also some recent blog-entries were written in the context of this opinion (JavaEE will die etc.) :-).

From my perspective a lean servlet/JSP project is also an Java EE project, because servlets and JSPs are a part of the Java EE specification. Nowadays it is hard to develop distributed, transactional, enterprise applications with Java, but without Java EE :-).