Because that's not what matched on when it searched for qr/CSV/ on the entire list of loaded "file" names. When you (string?) eval something it stubs in a representation of the location of the eval call and its showing you just the text that got eval'd there.

And again @INC and its ordering doesn't have anything to do with the order keys returns things for the %main:: stash ( a hash, but it's a special hash). If you have %foo = qw( 2 a 22 b 222 c ) then you similarly can't say what (grep /2/, keys %h)[0] is going to wind up returning.

Caveat: I am not a debugger expert. I actually learned this earlier today when I read your post, and then started playing around in the debugger to replicate. But I knew other monks were much better at the debugger than I, and could explain the f portion of your difficulty, whereas I couldn't. I waited until I read good explanations of that part, but since no one else explained how to see the contents of the file, I thought I'd now share what I learned, one debugger-newb to another.