starting/stopping contexts in Tomcat 4

[Mark.Abbott]

The ContextConfig.start and ContextConfig.stop methods in 
Tomcat 4b2 do not appear to be inverses of each other.
The start method causes children to be added to the context
during web.xml parsing, but the stop method does not remove
them.  Doesn't this mean that stopping and then restarting 
a running application will always generate exceptions as
ContextConfig.start tries to add already existing servlets
to the context?

    Mark