So you want to notify the 4 application instances of the change in the configuration manager.
JMS decouples the notification mechanism, so the client applications do not have to be running in order to receive the notification. The can receive the notification when they start up.
You could use JMX, EJB, RMI, a web-service call or a tuple-space such as gigaspaces, but this is slightly more tightly coupled as both client and server need to be active for the notification to be sent successfully.
This could be mitigated by building in an acknowledgment of receipt and resend functionality if necessary.
It may not be necessary, if you assume that the notification did not go through due to the application being stopped and knowledge that the application reads the configuration at start-up.
However this may not always be the cause of failure, it may be a network glitch or some other error which causes the notification to fail.
An alternative, as mentioned by ewernli would be to get the client applications to poll the config manager periodically, using any of the protocols mentioned above, changes would then be applied as soon as they are identified during the poll cycle.