Long routes linger after a connector goes down

[sharafian]

In this screenshot you can see that two routes (g.solstice and g.phobos) are extremely long and go through many nodes that exist elsewhere in the routing table. Pinging either of these destinations leads to a timeout.

It seems like the connector should be able to clean up these stale routes, or at least not rebroadcast them to its peers.