Current sfsb activation/passivation notification relies on read/writeExternal. This is semnatically not correct since replication also relies on serialization. So each replication would trigger a activation/passivation pair. I don't believe ejb3 specifies specifically activation/passivation to serialization (there is no word on how to perform passivation actually). So a better way is to decouple this.