service resource - inherited file handle weirdness

Check this out:

[root@chefdemo chef-repo]# cat site-cookbooks/autofs/recipes/default.rb
package "autofs"

template "/tmp/demo" do
source "demo.erb"
end

service "autofs" do
supports :status => true, :restart => true, :reload => true
action [ :enable, :start ]
end

simple enough? We run chef-client, it drops in the dummy template and starts autofs, yay. Let's check it out:

[root@chefdemo chef-repo]# lsof -n -p 11532
<snip>
automount 11532 root 3r REG 253,0 10 588386 /tmp/demo
automount 11532 root 4r REG 253,0 10 588384 /srv/chef/cache/cookbooks/autofs/templates/default/demo.erb
automount 11532 root 5r REG 253,0 10 588387 /tmp/chef-rendered-template.11449.0 (deleted)
<snip>

Eep.

If I remove the template and only use the service resource, those 3 file handles go away, but if I compare the lsof output of a chef started service definition versus just doing it from the command line, there's still 1 extra pipe being left open by chef.

Any thoughts before I start digging in?

Untested on other platforms. Happening with any template+service combo for me.