This is a small thing, but wouldn't be a good practice for firstboot to change the entry to 'off' with chkconfig after completing first boot activities? As a security practice, we tell sysadmins to know and tweak their services list via chkconfig. This setting stands out because it is named 'firstboot' and yet remains on after that; it's a bit ironic.
It's intentional that the firstboot in f8 does not chkconfig itself off, as this was a workaround for some corner case involving the timeout on the text firstboot interface. In f8 it's not doing anything other than checking if it needs to run and then bailing out, so there's not really any harm. Regardless, the next release of firstboot that I am testing in Rawhide will chkconfig off itself after running to completion so this bug will be fixed there.