Why can't a Stateless SEssion Bean implement the SessionSynchronization interface? it might also want to be notified of the transaction events.

It's just because a Stateless Session Bean does not have state. The container does not guarantee (like for the Stateful SEssion Bean) that the bean that will be used on two method calls, will be the same.