After deploying a MDB with Container-Managed transaction and
TransactionAttribute NOT_SUPPORTED, a RuntimeException thrown from
within the MDB onMessage() is reported to the Adapter as such, with no
EJBException wrapping. I.e.: the "((javax.jms.MessageListener)
endPoint).onMessage(message)" call in our adapter fails with the
exception type originally thrown.

This does not look compliant with EJB 3.1 spec(JSR 318: Enterprise
JavaBeansTM, Version 3.1, Table 20 page 392, last cell bottom right):
"Throw EJBException that wraps the original exception to resource
adapter".

Another part of spec I was just made aware of says this:

p383 of the spec states -

In the case of a message-driven bean, the container logs the exception and then throws a javax.ejb.EJBException that wraps the original exception to the resource adapter. (See [15]).