I too have this issue. It was so bad that my previous iMac had after-image burn-in on the monitor. I believe the afterimage was temporary and would clear in time, but after coming home the computer had not engaged the screensaver or put the display to sleep. I found that bringing up a grey window showed text from the previous window that had been displayed all day.
I thought it was a hardware issue with Mavericks and my circa 2007 iMac. Sooo, I bought brand new iMac last month- the latest model 27inch (all maxed out). I transferred the accounts over from the old iMac and thought everything was working fine. It appeared to be fixed...
Then last night I decided to install a few 3rd party screensavers- the helio, fieldlines, hyperspace, etc...really cool GL screensavers that are free. After doing that, the screensaver no longer kicks in and if I go to the screensaver corner the screensaver kicks in for maybe 4 seconds and goes away.
I don't know what Apple has changed- I too had hoped for a fix in 10.9.2, but I don't even see any acknowledgement of the problem on the internet outside of user reports. The "fixes" I've read about don't work for me either- and I doubt they actually work long term for anyone else- I think the changes they ask you to make simple result in the screensaver management process restarting and working fine for a while. I've notice with the old 2007 iMac that the screensaver would work for a while after a reboot...but eventually stop working.
Apple really needs to address this ASAP. Like I said, I've had visible monitor damage as a result of leaving the old iMac on without screensaver or power management kicking in. I had tried a number of "screen cleaners" like JScreenFix to get rid of the ghosting and they worked to some degree, but I don't want that to happen to my brand new iMac. If it does, I'll expect Apple to replace it under warranty given that their OS simply doesn't work.
I'm going to try deleting the non-apple screensavers and rebooting to see if things go back to normal. I'd be curious to know if anyone else uses custom screen savers? Maybe its a 32bit vs 64 bit thing? Could it be that if you install a 32bit screensaver the screensaver daemon switches to 32 bit and that has the problem? I recall a while back that some preference panes would only work if the preferences manager switch to 32 bit.