I haven't found this to always be true.  See the comments in PE-3140 (Abort TK JVM process if Jetty port already bound at startup) -- https://tickets.puppetlabs.com/browse/PE-3140.  In services that have no dependency on *trapperkeeper-webservice-jettyX*, the thrown `Throwable` from either `init` or `start` did result in the whole JVM process being shut down.  For services that do have a dependency on *trapperkeeper-webservice-jettyX*, however, the thrown `Throwable` from `init` did result in the whole JVM process being shut down but the thrown `Throwable` from `start` resulted in the JVM process indefinitely hanging.  If a service were to have a dependency on another non-Jetty service, though, I've seen that the thrown `Throwable` during the downstream service's `start` would result in the JVM process being shut down.  Not sure yet what it is about Jetty which is unique here but I'm wondering if we want to either include something about this exception here or just leave this paragraph out altogether until we've fully characterized the behavior.  I'm leaning toward the latter.