Also, given the rather largeish updates to the language plumbing in 10.7 and 10.8, including ASOC access to AppleScript editor, the idea that Apple isn't supporting and improving it is simply incorrect.
Citation? As previous poster says, Apple don't even bother producing release notes for it any more. The last significant developments were Intel support, AS 2.0 in 10.5 (mostly cleaned up Unicode support) and ASOC in 10.6. And both were tiny projects by Apple standards; enough to keep an AS engineer busy, but that's about it. Enabling ASOC to work in ASE was a minor tweak. Look at the number of developers working on something like Python or Ruby. Now look at the number of developers working on AppleScript, and bear in mind their time is split across a whole bunch of other automation-related technologies as well.
Meanwhile, there's a long list of AS-related stuff they're not doing, including stuff like QA, documentation, education, evangelization, or even just supporting it properly in their own applications. Whacking coffin nails in most of the Carbon APIs isn't going to do AppleScript any favors either. Apple simply doesn't care about AppleScript or scripting in general, recently reversing an earlier plan to include the excellent and popular MacRuby in OS X. The only language they care about is Objective-C, because that's what puts apps in their App Store, and money in their pockets. And their future OS X + iOS strategy for inter-process communication is clearly based on XPC Services - i.e. low-level, ad-hoc, ObjC developers-only - which doesn't bode well for Apple events either.
I don't think Apple will outright kill AppleScript (at least not for now); why bother creating [minor] user backlash when there's no immediate need for it? They'll just keep sucking the life out of it until there's nobody left to care.