Pavel Sturc Current aproach for resolvers/subscriptions is not going to work properly and requires refactoring. This is really important bug to have
(along with other one where resolvers are not removed when schema changes), however from my point of view there is no sense to invest time.
Subscriptions can be generated basing on directives - we can avoid sending them at all, however this requires bigger discussion.
It's best to collect this issues and have sprint to resolve them, but I think we are not ready yet to.

Ideally this problem will require feature:
When schema is saved we need to verify if there is no orphan resolvers and possibly subscriptions that we can remove.
There are couple related bugs that will be resolved in one go when we will implement this, however from technical perspective is best to do this after projects abstraction will be added.