consider whether the same instance of a ServiceStateChangeListener should be allowed to listen to events

Currently there is no limit on the number of times a listener can register for events; it's a simple list. A service must unregister the same number of times that it registers.

Is this the desired behaviour? If so it should be documented in the Service interface rather than just implicitly in the AbstractService implementation.