Currently plugins don't really get disable on plugin.disable().
Expected behaviour:
onDisable() is called
- the startup is interrupted at the point of error and will be aborted
- all registered services, commands and so on get unregistered
- the plugin is put into a sleep state