Well - I think erik's explanation is substantially correct.
Actions have been reworked over the last couple of releases. The theory is that it is the actions should be built in PortalModuleBase, which has all the security knowledge and the action menu and action buttons should just show what is available.
In previous versions, the logic to manage was littered all over the app (Skin.vb, PortalModuleBase and even in the ActionsMenu and ActionButton).
In the current behaviour if an item is visible (it should display in the menu and in the button).
I agree that we may need to tweak this, but the current behaviour fixes quite a large number of wierd behaviour requirements. For instance, prior to these changes adding an ActionButton to a skin required an ActionMenu in the skin (even if it was not visible).
The logic should be changed to show the Print/RSS buttons, but as discussed above this wil display the Action menu.