Given that we agree on the general principle, and I have had my chance to voice my rant, let's dig further into the underlying issue. Is putting the JBoss Embedded runtime in Tomcat's classpath an unreasonable request? (this is a real question, not hypothetical) In Seam 1.2.1, it was possible to use the embeddable EJB3 per application (it went in the WAR file). In Seam 2.0, a move was made to the JBoss Embedded runtime. In doing so, the Seam developers drew that conclusion that starting an JBoss Embedded runtime will work if a single WAR file is deployed, but would cause a problem if multiple WAR files tried to use it. It might be possible to get the JBoss Embedded runtime working from within the WAR again, but the limitation of multiple WAR files would remain (without additional work). Let's answer the first question and then figure out where to go next. We should also give instructions for how to use Jetty if we are going to put forth more information/fixes for Tomcat. However, if the answer to the question above is "no", then we should move on to doing the same with Jetty. By the way, a move from Tomcat to JBoss is pretty easy. At my business, we develop on Tomcat/Jetty and then go to production in JBoss (we aren't deploying any Seam apps yet). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089033#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...