Read Literate Programs
Explore code bases that use a literate programming approach (as introduced by D. Knuth), it will help greatly.
For instance:
Read Good Example Projects
Some other pages are very well documented and can be of good help to see either good practices, bad practices, and practices that are good in constrained environments but may make your code hard to read and maintain. By the way, you mention jQuery as something you don't want to use... but reading jQuery's source might also be a good idea, as well as the source of other frameworks.
GitHub, Google Code Project Hosting, Google CodeSearch and other online code hosting and browsing tools will be your friends here, and there are plenty of good projects that use a load of JavaScript.
Have a go at the following ones to see what I mean (in no particular order here):
Read Good JavaScript Programming Blogs or Essays
You may want to look for a few blogs to follow for yourself.
I don't really want to point out anyone in particular. Tastes vary, both in terms of writing style, coding style and programming paradigms. That being said, learning from people using techniques you dislike is also very enlightening.
Here are still a few for pointers:
Experiment with Different Frameworks
And this, extensively: read the code, follow the tutorials, do benchmarks.
Here are some for a start (in alphabetical order):
Sure, they will hide some of the complexity for you. So be sure to understand what's happening under the hood.
Have a look at what JS can do for you in other environments - not only on the client side - as well, for instance with node.js.
Teach yourself about the Interpreters
They run your stuff, so you better know what they can and cannot do, and how it impacts your websites rendering and performance.
Speaking of Benchmarks...
If you need to test this (and take the habit of doing so), meet your new friends:
Have a browse on the above to see great examples people published.
ECMAScript Standard
The ECMAScript standard exists for a reason. Read it, even if it is (or appears) unreadable. ECMA-262, 5th edition, is your bible for the stuff under the hood reference.
Still some complements to the standard might help...
Have a look at Google DocType and Mozilla's JavaScript Reference
Lurk on StackOverflow
Follow the tags for javascript/ecmascript questions, or for a specific framework, and read great and bad answers alike. Annotate them, comment on them, and don't hesitate to try to answer. Worst case scenario, you write a perfect answer, get tons of points and have made someone else's life easier. Best case scenario, you get shot down in flames, learn a bunch of new things, and get on to the next question to dig deeper.
Don't forget to have a look at the highest voted JavaScript questions.