Tracked down the source of the Threadstate's Stackoverflow exception! BroadcastToUsersInRoom  inside GameUtilities was attempting to SendDataToPlayer using the playerID of the client who just disconnected, so the data couldn't be sent because the thread state was hosed! For whatever reason, my checks to make sure the player we're transmitting data to was still connected would result in the exception being thrown anyway.