The TransporterServer automatically tries to load a remoting detector (to allow for autodiscovery for transporter clients). JMX is used to tie detectors and remoting servers together. There is not dependancy on JBoss JMX, so any JMX implementation jar on the classpath should work.
This tie between detectors and servers being reliant on jmx will be removed in the future.
As for jars that are required, we don't have formal documentation for this yet (http://jira.jboss.com/jira/browse/JBREM-311). The transport implementations are lazy loaded, so won't need transport specific jars unless using that transport (e.g. only need tomcat jars if using http invoker).
Thanks, great news to me.