I think your problem stems from the fact that a MDB is only allowed one message listener interface.
See EJB 3.1 FR 5.4.2.
If you want to create a JBoss extension that would allow multiple interfaces please do so on AS 6 code base.
thanks for the suggestions so far. As I understand, the container must decide which is the message listener interface. This can be done safely by using the 'messageListenerInterface' element of the 'MessageDriven' annotation in the case that the MDB implements multiple interfaces. But why MessageInflowLocalProxy which is a JBoss specific class can't implement ALL of the MDBs interfaces? It's a proxy of the MDB and it should implement all 'physical' interfaces not only the detected messageListenerInterface in my opinion. Is there any reason why this is not the case?
What do you mean with "...if you want to create a JBoss extension..."? Is there any extension mechanism? Can you point me to the right direction here, please?