Stopping CXF consumer route does not stop the underlying Jetty Server

As described in DEV-3031, when a CXF consumer route is removed and another (with different address/port) is added, the old endpoint still remains. There is a test case in DEV-3031 demonstrating this but you can easily see what is happening by just spinning up a CXF consumer route and stopping or removing the route at runtime through JMX. After the route is stopped/removed, the underlying CXF/Jetty endpoint is still up. The next time you create a similar route, it seems to reuse this endpoint and not create a new one with updated address & port.