From the same Metasploit instance, there's really no point in having two handlers watching the same hop; as long as there is one handler watching a hop, any new session that comes in will be recognized and all sessions currently using the hop will be handled.

If you are talking about having multiple Metasploit instances from e.g. different pentesters using a single hop, the limiting factor is in the fact that when a new session comes into a hop, there's no way of determining what metasploit controller would own that session if you have more than one. You would have to build a new identifier into the payload (or use a URL prefix or something) and then build a new identifier on the handler so that the hop could give each pentester their respective sessions.