Undefined resources causing weird subscriptions

Yesterday I was working on #80 websockets when I noticed that in many situations, the data browser will `subscribe` to `"undefined"` resources. This happens when a new resource is created without passing a Subject.

I'm not sure when this happens, but I need to deal with this, as it causes unnecessary subscribtions later on, and it probably also causes _missed_ subscriptions.