Can dbus tasks be prevented from launching in an X session?

Issue

An application launched via Exceed X Server fails to manually migrate to a second cluster node after service shutdown on first node.

Expected behaviour is for the X server to reset when all X clients on the prior session are terminated. However, there are still remaining open connections to the X server. Exceed Transport Monitor is used to determine that there are blank named entries remaining on the X server.

This causes the other node when it fires up the application to get a corrupted display.

Desired behaviour is for NO dbus tasks to be started when the application clients are launched.