Ah check. I was worried for a moment that even this wouldn't work, but apparantly thread.current also [works with fibers](http://devblog.avdi.org/2012/02/02/ruby-thread-locals-are-also-fiber-local/). We'll switch to that then, thanks :)

For us performance would be a nice to have, but currently has no priority for us (as in, we're not going to spend a lot of time implementing it at this moment).