I've run into the following battery drain bug twice now (once on GM, and once yesterday).
Using XCode Instruments, I have figured out that Springboard, Backboard, and Mediaserverd seem to flip out for no reason, and run at 10%~ cpu each, constantly (even when idle), and will cause your "Usage" stat to increase at the same rate as your Standby time (this is the best way to see if you have this bug - check your "Usage", close all apps, put phone into standby for a few minutes, and re-open = has your "Usage" increased in idle?). The bug also drains your battery at a good rate of 1-2% every 5-10 minutes.
I can't figure out what triggers this to happen, but I noticed yesterday my "Usage" had hit 4 hours, when I'd barely used the phone 1 hour in the space of a day. I thought back to what I may have been doing 3 hours ago to coincide with the phantom usage, and I only remember briefly opening my iPhone to use the Camera app (took no photo), and open Messages/Photos).
At the same time, I noticed that keyboard and lock screen sounds were really weird - pressing 1 key had a good 1-2 second delay to play the sound, typing multiple letters produced no sound except a single sound at the end, and locking the phone had a significant delay in playing the lock sound. I can't figure out whether the bug lies in Mediaserverd (seems the most likely as system sounds were affected) or Springboard/Backboard. Toggling the silent switcher off and on would occasionally alleviate this somewhat, but my best guess is some system sound gets stuck (possibly produced by the springboard/backboard processes)... but I can't figure out what or why (typically my phone is set to silent anyway). I suspect the lock sound may be the problem, as my guess is that, like Android, the system still triggers the sound event when the phone is set to silent - so, it's entirely possible it could get "stuck" somehow (the keyboard sounds, or any other system sound could get stuck also).
This is all fixed easily by just restarting the phone, but I could not figure out any way to fix this without a restart. Typically speaking, iOS10 has much better idle CPU usage than iOS9 though from my testing, so that's a good thing...