Major Description
The current design of the jetty integration is that the Jetty server is a hidden, static, shared, resource of the buses. This is fine, until someone wants to create (and perhaps clean up) a completely self-contained environment. It is a tradeoff: the current design allows an app to make multiple busses that deploy services on the same HTTP port(s), but it offers no direct way to control the lifecycle of the server.
I would propose, as an idea, a property on the http engine bean which controls this. If set to the non-default value, the engine will be considered a resident of the bus. If it thus ends up on a fight over a port with some other server associated with some other bus, so be it. When the bus is shutdown, such a server would go away. Period.