One note on the 3.0 SDN Dialog Listener. When you install this on a Front End, it removes any previous SDN22 Server Applications in the Central Management Store. This doesn't affect running dialog listeners but it will when the server is rebooted or the dialog listener service recycled - resulting in the listener service never starting. The services will not be able to connect to SfB throwing a "Application Unauthorized" result.
Our work around was to issue a New-CsServerApplication for each pool once all the listeners were installed (30 front ends), thus repopulating the central management store.
Another learning is that once the dialog listener is installed it must wait for replication before the service will actually start. You can monitor this in Event Viewer. You should NOT start another dialog listener installation on another server until the current installation service actually starts. This is because of the aforementioned learning that the installer removes all previous entries. If the second installation completes and that server replicates faster than the first, the first one will never start the service because it's entry in CMS is now gone.