I have concluded that it is possible (with the same explanation as is used the Session Beans): "the use of message-driven bean classes as superclasses merely represents a convenient use of implementation inheritance, but does not have component inheritance semantics."
in other words:
"A listener interface exposed by a particular message driven bean is not inherited by a subclass"
Message Driven Bean A exposes the message listener interface Echo and Message Driven Bean B exposes the message listener interface Talk, but not Echo (unless explicitly put as an implementer).
I guess this is a theoretical discussion as I can not think of any practical solution where you would need something like this.