Agreed that it is a bug. The question is whether it even makes sense to use the thread handle or thread ID.
Who is using apr_os_thread_current() and if so, what are you plugging it into?
FWIW, flood is using it as various locations to provide unique per-process ids (OpenSSL requires unique thread ids in order to be threadsafe). But, it's not passing them to a native OS call, so the value doesn't really matter. -- justin
