Update RequestService.cfc

since fireing runevents within different threads does result in overwriting prc which is not wanted especially when writting multiple modules which can run standalone and within threads and you don't want to programatically check for thread or not.

getContext enhanced with a subscope in case threads makes sure each thread has it's own requestcontext. the initial context for each thread is copied from the default on.

in my opinion it's not necessary to exchange data from thread to thread via reqestcontext, but it can be solved when the thread is join in the application or through an other scope. therefore this seems the most straightforward solution to the problem ;-)