Reading from the linked article I would assume that they were kind of running out of time for the feature freeze.
I would expect the querying functions to be added in the release after this, or before in form of an extension.
I'm not on their core developer mailing lists, but I presume this is because of a prioritization of stability over most everything else.
They'll take a stable half-feature over a buggy full-feature at any given deadline. What matters is that over time they patiently and carefully expand those half features.
The most visible example is the slowly increasing coverage of replication. This JSON feature is another example -- I expect it will grow in future into a fuller feature set.
They already have that: http://www.postgresql.org/docs/9.1/static/hstore.html
The Heroku Postgres guys have been playing with this idea [2] using the PL/V8 plugin, which embeds Javascript as a supported language inside Postgres (and thus makes it trivial to implement the json_project_key function), but if Postgres is going to natively support JSON parsing then it shouldn't take an addon module to achieve this.
[1] Attempting to forestall the thread-jacking: I know NoSQL databases have other benefits besides their data model, but for some applications that's certainly one of the benefits. [2] https://gist.github.com/1150804