Fix #60: Performances issues when adding or removing multiple resources

Instead of calling ServletContainer.reload everytime a resource is registered a scheduled executor is used now. This executor checks the dirty state of the RootApplication at a configurable interval (2500ms default). If the RootApplication is dirty the ServletContainer.reload will be triggered.

Basically this introduces bulk resource registrations.
Merge branch 'issue60'