Asynchronous Invocations are not supposed to be part of the callers transaction because there is no guarantee that the async call is executed in parallel or after the caller already ended.
This will cause warnings and exceptions if the asynchronous call is trying to use the transaction while the container is commiting or rolling back the transaction.
It will break compatibility when migrating from earlier version (<=7.0).
According to the EJB specification
The client’s transaction context does not propagate with an asynchronous method invocation. From the
Bean Provider’s point of view, there is never a transaction context flowing in from the client. This
means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous
method are exactly the same as REQUIRES_NEW.