I usually list off areas of specialty/expertise seperate from "technologies". Applying for a .Net position, not many are looking for a JQuery expert, so I try not to let that take away from my true specialties. It might look something like this:
Expertise: C#, MVVM WPF, WCF
Technologies: JQuery, Linq, Entity Framework, Windows Workflow Foundation, RPG
This prevents the situation that can really bite you: when a hiring manager counts certain technologies as actual negatives against you. Of course it is irrational, but most people cringe a little when they see outdated technologies on a CV. In our area its fairly difficult to find .Net people, but there are loads of AS400 RPG people. A lot of the RPG people will learn just enough C# to get in the door, but after 6 months its realized that although they can code, they're fundamentals are from a totally different platform, and they stuggle to pick up the most basic language dependent design patterns. Obviously, its not everyone, and I know some real wizards who spent years on COBOL, but it doesn't stop people from thinking twice. If you don't want to totally leave that skill of the list, putting it in a sublist can be a good option.