Incidentally, I'd probably include some form of assembly as well, for the whole "must understand the underlying hardware" aspect.
Eight should be enough, after that, you probably wouldn't learn enough to make the effort worthwhile (except maybe to learn a language for a particular need, eg available libraries). I think my number seven then would be an assembly language and my eight would be Oz, ATS[1] and J[2] (not really in the same category, but more of a misc interesting languages category). I would then add Python/Ruby/Boo/Groovy in with C++, C# and Java.
ATS and J are both unique in their own ways. I'm not sure what value there is in learning either of these (since I don't know them) but they seem different enough to teach you something new. J (or APL or K) do teach you about array processing languages and point-free programming, so maybe this is useful. ATS is interesting because of its emphasis on types in a way I haven't seen in other languages:
PS: Turns out I spelled Lustre wrong :-D
For what it's worth the list I had mind originally was something like:
* C, for low-level procedural and machine-awareness
* Ruby, for high-level procedural and OOP (plus scripty perl-isms)
* Scheme, for distilled lisp-iness without distracting details
* Haskell, for HM static typing and functional purity
* Two empty slots to cover languages I'm less familiar with
After seeing your list, I realized I'd carelessly underestimated the number of empty slots necessary...
Yes, there are gaps - I'd also add Oz, Python/Ruby/Boo/Groovy and J into the mix to get a more fully rounded paradigm tour and, even then, there are some things missing, though at this point you should have a strong knowledge of languages and paradigms and should be able to tackle most problems pretty well - or at least, know enough to choose a good programming language for the task at hand.