Not sure about the exact problem but if you are happy to run the embedded Tomcat server just download the JBoss Tomcat bundle and install it. JBoss will start the Tomcat container as a service in the same VM. The current 3.2.x releases have the JBoss Jetty bundle as the default - Jetty being the servlet container alternative to Tomcat. I prefer it, having migrated from two years working with Tomcat.
Intra-container calls (servlet to EJB) are much faster - let's say that a ball park figure is at least by an order of magnitude although my performance tests show by two orders. Since this is a democratic society, some people wish to operate Tomcat as an external and physically separate entity to JBoss. This allows many additional features of Tomcat to be used - although the developer needs to make a decision about whether the tradeoff in performance is worth the additional features. So that is why there are choices about your JBoss Tomcat, internal/external configuration.
However, if you just take the JBoss Tomcat standard bundle, Tomcat will run from the box in the JBoss microkernel environment, HTTP on port 8080, HTTPS on 8443 and AJP13/JK2 on 8009.
Hope that helps.