DefaultMessageListenerContainer is sort of an issue because it opens threads. On WildFly you have ManagedExecutorService available which should make it possible to make DefaultMessageListenerContainer use JBoss threads.
You should be able to deploy our application as a WAR or EAR. Even if you just use a server or ejb to kick off spring.
Thanks. In fact I was able to kick it off packaged as a war, didn't try and ear or using an EJB to kickstart it.