Yes, too much information is a bad thing. You'll want to limit it to things that are relevant. This can mean two things:
For your generic CV, the kind that you display on websites and send to companies without specific positions available, make sure to focus on what you're good at, and want to work with. Put the best ones at the top; anyone skimming your CV will likely read only the first two or three items.
When responding to a specific job-opening, create a custom CV that highlights the skills that make you a good fit for that job. Again focus on things you're good at or did a lot with, over things you've done little with.
In general, leave off things that you don't know much about. This is not relevant to companies anyway; the difference between someone who once spent a few hours doing Haskell and someone who never did Haskell is meaningless. If the job is about Haskell then you're both unqualified in terms of experience, and if it's not about Haskell then it's irrelevant either way.
If you feel that your experimentation with different languages is an asset, then mention it as one of your positive points, but not under experience.
"Enjoys learning new languages" gives you a bit of personality, while "Did two weeks of Haskell" does not. If you are the kind of person who tries out new things, that can be valuable in companies, but it's the trait and not the result that matter.