Server concurrency limiting isn't enforced when no state is initialised for a user

[peppy]

The current method of ensuring state consistency across (potentially) multiple connects and disconnects by the same user is to clean up any state which is owned by a previous user before allowing a new connection on the server.

This works fine.. until the same user connects twice to the server, not taking out a state either time. You now have a situation where there are two connections from the same user potentially sharing state data.

[bdach]

I believe #80 should cover this, so closing.