Errors logged after a Performance module is removed - Could not connect to pm4_WriteEngineServer

Customer reported they moved drboot 4 and then disabled pm 4 successfully, but a process was still trying to communiate to WES on pm4 when it's in a DISABLED state causing the following log to be issued.

Nov 5 14:23:18 usfit-hdpdev-m01 joblist[81935]: 18.382173 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos6/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm4_WriteEngineServer: InetStreamSocket::connect: connect() error: Connection timed out to: InetStreamSocket: sd: 739 inet: 192.168.213.128 port: 8630
Nov 5 14:23:18 usfit-hdpdev-m01 joblist[81935]: 18.535189 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos6/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm4_WriteEngineServer: InetStreamSocket::connect: connect() error: Connection timed out to: InetStreamSocket: sd: 744 inet: 192.168.213.128 port: 8630
Nov 5 14:25:41 usfit-hdpdev-m01 oamcpp[181503]: 41.801886 |0|0|0| E 08 CAL0000: OamCache::checkReload shows state for pm4 as MAN_DISABLED
Nov 5 14:28:10 usfit-hdpdev-m01 joblist[81935]: 10.952291 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos6/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm4_WriteEngineServer: InetStreamSocket::connect: connect() error: No route to host to: InetStreamSocket: sd: 22 inet: 192.168.213.128 port: 8630
Nov 5 14:28:13 usfit-hdpdev-m01 joblist[81935]: 13.953383 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos6/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm4_WriteEngineServer: InetStreamSocket::connect: connect() error: No route to host to: InetStreamSocket: sd: 22 inet: 192.168.213.128 port: 8630
Nov 5 14:30:21 usfit-hdpdev-m01 oamcpp[184321]: 21.818101 |0|0|0| E 08 CAL0000: OamCache::checkReload shows state for pm4 as MAN_DISABLED

Procedure customer used :

1. Active system with 1 UM, 4 PM , local query, and 1 dbroot on each PM.
2. Stop system.
3. Move dbroot4 off of PM4.
4. Disable-Module PM4
5. Add dbroot4 to PM1
5. StartSystem. No issues,
6.. After some work, shutdownsystem.
7. Start system. System is active, showed the PM4 was disabled.
8. No issues in system. Selects, DML, DDL, cpimport all good.
8. PM4 server was powered off, then PM4 shows now as man_disabled/degraded.