Your idea of wrong destructor timing made me take a second and deeper look at Hook::LexWrap (and some inserted print statements), and I could produce another core dumping script, which should trigger the same error as Hook::LexWrap with IndigoPerl :

#!/usr/bin/perl -w
use strict;
use warnings;

my @a = ();
my $foo = bless \@a, 'Cleanup';
print $foo;

package Cleanup;

use overload
  q{""}   => sub { undef },
  #q{""}   => sub { "foo" },
  q{0+}   => sub { undef },
  q{bool} => sub { undef };

1;
[download]

It now seems to me as if the stringifying dosen't work correctly, because everything works fine if the second variant of stringifying (returning foo) is enabled. Destructors don't come into play, as I'm not defining any destructor anymore, it seems more like it's a stringify problem with classes that stringify to undef...

perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ;    # The  
$d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider
($c = $d->accept())->get_request(); $c->send_response( new   #in the
HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' #  web
[download]