Is there ever a need for more than one TRANSPORT route

I am using the TRANSPORT and self-routing and it works great. My question is: is there ever a need for more than one transport route when using multiple services, or should there just be one per database, generally speaking? What exactly does the presence of this route tell service broker? It seems as though it just signals service broker to use self-routing if it can't resolve the service any other way....similar to the way the LOCAL route works, only for remote services.

You are right, TRANSPORT routes are expected to be one per database. Its presence indicates that self-routing names are valid to route messages to the destination.