If it OOMs on Tomcat, then you have to update the (remoting) libraries on Tomcat too.
I took the jboss-client.jar from the 8.2 release for sure .
As I mentioned before, only the workaround solves the problem - on both sides (wildfly and tomcat).
Just for information:
I found out that the original wf8.2 download has the jboss-ejb-client-2.0.1.Final.jar module included.
What about this version jboss-ejb-client-2.0.2.Final.jar:
At the moment I could run the EJB driven applications for one week.
I will apply the jboss-ejb-client-2.0.2.Final.jar and see what will happen.
I have a similar setup as yours and I am running into the same issue. The workaround "-Djboss.remoting.pooled-buffers=false" makes it better and tomcat runs longer before giving an OOM. But when I run a load test, tomcat crashes due to an OOM. This did not happen with jboss version 6. Did changing the jar to jboss-ejb-client-2.0.2.Final.jar help you ? Or, did you find any other solution?