Coupled with OS X 10.9's "race to sleep" and they also may be able to do "blast, recover, repeat" cycles on a wide variety of workloads that will deliver acceptable user action/response. Non human driven workloads are the only loads that typical drive the engine throttle to 100% power and keep it there for extended periods of time.
There is also slop/safety factor in TDP specs also. If Fred, Barney , Wilma , and Betty all design different components with different coolers there is typically a small factor built in to account from the possibly conflicting designs. If Apple carefully measured and removed the margins they could punt on power/disposal that never gets generated/needed.
Doubtful all of these brings things all the way back to even, but it probably isn't quite as ridiculous as it looks. However, high enough that 6, let alone 7, TFLOPs is going to largely be a mirage on anything be the most contrived codebase+dataset.
Or not running them all at the same time. The common trait where all the CPU and GPU packages are going is that they don't run at a single speed. It is all about dynamic range. The computer should down clock when there is nothing to do.
All great points, I am highly skeptical though. The TBD on the 6/8 core E5 is 130 watts (12core is less). So now we have a TPD of 678 Watts, not including the USB or TB ports. That means Apple has to find a way to shave off 34% on sustained tasks.
What will happen if it hits the wall? My hope is that it'll just down-clock to oblivion, my fear is we're going to see nMPs blinking off.