To reproduce this issue disable a WTMS service (a global one or a virtual one) and restart GeoServer. The disabled WMTS service will be re-enable.
This happens because the service initialization, which is supposed to only fill the blanks, is blindly enabling the service:
This is situation was not catch by the unit tests because the initialization is not invoked as it should be:
Mailing list discussion: