Well, an educated guess could be that the designers didn't even want to open the risk of MDB creation being performed on demand
In any case even the maintenance & expansion of the
EJB pool for MDBs is controlled "anonymously" by the container - no where we ask explicitly for a MDB instance. However if you need the notification, you can still have one ejbCreate() inside bean code, right?