The original Intel HD Graphics were pretty bad, choppy animations even on 10.6. That chip was so bad Apple chose to release the 13" 2010 MBP with the old C2D CPU's so they could use the Nvidia 320m instead.
Actually that was because of the license spat between Intel and Nvidia. Nvidia had a license to make their own chipsets and Apple used them in the first Unibody machines because they saved a lot of space by having the chipset and the graphics on one chip. Apple would have kept using them if Intel hadn't gone and (successfully) sued Nvidia saying that the license was only for Core 2 Duo chips. This is why it took so long for Apple to release their first Arrendale/Nahalem machines when they had to bolt a Nvidia GPU to an Intel chipset (rather than getting them in one neat package from Nvidia) and these boards were simply too big to fit in the 13" machine without having to scale down the battery.
according to this the highest supported on Windows and Linux is OpenGL 3.1. With that being said, I'm unsure in the case of HD 3000 on OS X whether the reported OpenGL 3.3 on the chart points to hardware capabilities but OpenGL 4.1 functionality is emulated in software mode.
The source reference for Windows is from 2011 and the source reference for Linux is from 2012. As for 3.3, it's basically the same as 4.0 except for older hardware, the two were after all released at the same time.
Nvidia's had OpenGL 4.4 beta drivers for Windows and Linux since July and AMD's only got support for 4.3 on both platforms (thou the Linux driver is a lot buggier than the Windows one).
On topic:
Any news on a fix for the video output bug that showed up in 10.9.2? Apple has recognized this bug (someone from them even emailed me after I posted about it on the support forums) and it's fairly annoying when I have to fidget with both a miniDisplayPort-to-DVI adapter and a 3,5mm stereoplug when I used to be able to do it with a single adapter AND get better quality audio.
Turns out it's some kind of kernel extension bug in the graphics related ones and when I tried to fix it by replacing one of the broken extensions I broke OSX. Sure taught me not to mess with the kernel extensions the same way Windows taught me not to mess with the registry.