I think that purely from the spec point of view the Mdb27891072#setMessageDrivenContext() method should not be intercepted as it is not a message listener method . And CDI 1.2 is clear that only invocations of message listener methods of message-driven beans are passed through method interceptors (see also 7.2. Container invocations and interception). Also the EJB 3.2 mentions that "AroundInvoke interceptor methods may be defined for business methods of sessions beans and for the message listener methods of message-driven beans", see also 7.3 Business Method Interceptors. CDI 2.0 wording is a little bit vague though - see also 23. Interceptor bindings in Java EE.

However, I'm not an EJB/MDB expert and I can not judge whether it could have some practical impact.

In any case, it's the responsibility of an integrator (WebLogic) to use the Weld SPIs in a way that complies with the specific spec (EJB) requirements.