We should probably avoid relying on globalWorld when we don't have to. In this case, client has a world, so we don't have to.

globalWorld only exists because it was the easiest way to get the http service to talk to a world instance. Eventually we could add the ability to have multiple worlds on a single server (unlikely, but we still don't want to have to make it difficult unnecessarily).