Had no problems pre mysql version 5.0.21.  After an upgrade of mysql the slimserver started spitting out the following errors.

2006-07-20 23:44:06.8350 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391
2006-07-20 23:44:06.8492 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391
2006-07-20 23:44:06.8634 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391
2006-07-20 23:44:06.8991 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391
2006-07-20 23:44:06.9133 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391
2006-07-20 23:44:06.9751 prepare_cached(SELECT id, role, contributor, album
FROM   contributor_album
WHERE  album = ? AND role = ?
) statement handle DBIx::ContextualFetch::st=HASH(0xa8e8cc8) still Active at /usr/local/slimserver/CPAN/Ima/DBI.pm line 391

Not sure if this makes sense, but I've found a few articles http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/sld031.htm.  One thing I tried was upgrading DBIx::ContextualFetch, DBI, DBD::mysql..etc and other packages to the latest versions in my perl installs.  I then transferred them to the appropriate CPAN dirs, to no avail.  Also DBD::mysql, I think, now requires some .h files from mysql-devel to build.  Either way, still couldn't get the messages to go away.  The CPU on the box pegs 100% every time a UI web page is loaded, which started after this error showed up.