By that I mean, rather than try to decide what is good for a tutorial, just go grab a book and write a tutorial to accompany it. This does several things:

1. It gives you a good starting point as well as a way to focus your efforts
2. As Brian d Foy said, you can't show them everything at once. So show them a little and let them reference the book in an obvious manner for more information. Let the book and tutorial leverage each other
3. Maybe your efforts will start a trend for other language texts and not just beginner texts.
4. Your initial work can be expanded on later to provide more advanced tutorials on the same subjects.

Personally, I've always hated examples in books as they tend to be excissively simplistic or just plain contrived. Then of course, sometimes they just don't work :-) Having running code examples that walk through and explain each and every action showing side effects, etc. would sure be more interesting than a static code snippet that may or may not even run as printed...

Some may consider this dangerously close to copyright infrignement. I don't think it is but won't go any closer than this to that discussion other than to say if the book can be used as a text for a class, this use should also be acceptable.

Obvious suggestions are the O'Reilly books, "Learning Perl" and "Programming Perl". For a slightly more advanced and disjointed tutorial, "Mastering Algorithms with Perl".