Okay, I'll add my frustration here as well.
I've had this problem too, and more noticable since the 1.4 update.
I posted a thread similar to this here.
But I'll just copy over what my main problem was...
Whenever I plug my computer into my Cinema Display (with the computer closed) it won't wake up fully. The status light will come on, any external hard drives will spin up, but the display won't turn on and the computer will go back to sleep.
I have to restart the computer manually to get it to work normally, and if I disconnect it while it's between the sleep and wake mode and try to open it, the backlight will come on but the screen will remain black, causing me to have to force restart it.
This is in addition to my first problem with the backlit keyboard not coming on automatically after sleep, which was temporarily fixed by resetting the SMC, but it goes back to the problem after a week or so.
What could be causing either of these problems? Could it have something to do with BootCamp since I have it installed, or is there a defect?
I would bring it back to Apple, but there's a small dent in the front right corner, and I'm afraid they would deny any problem I have.
I took my MacBook Pro (2011, i7 2.2, 17") into the Apple Store on Monday, and after about an hour of attempting to replicate the problem with a different monitor, there was only one time where there was any sort of problem.
The employee told me to see if there will be a fix, or otherwise they will replace the logic board for me.
One thing I'd like to add as a note...
It seems that the problem is more prominent when I have my computer with everything on it as usual. As in, before I took it to the Apple Store I performed a clean install of OS X, and that may be related to how bad the problem is, any opinions?
I had attempted at reinstalling OS X from a Time Machine Backup, but the problems continued shortly after completetion. In addition to this, I clean installed OS X, and manually reloaded my applications and media, hoping that the problem had stemmed from some kind of broken file system that could be repaired by a new install.
But no matter how I do it, the problem comes back despite the method. It is really something I want fixed, as I pretty much only use it in clamshell mode when home...