Production Package Reverts to Development Package Configuration Values When Run By SQL Server Agent

Hi, I have a SSIS 2005 package that uses a SQL Server Table Package Configuration and I'm using a SQL Server Alias for my configuration database connection string.  When I manually execute the package in our production environment using SSMS (the Execute Package Utility), it properly accesses the production package configuration and data.  When I initiate the execution of the same package using SQL Server Agent, the package reverts to the development package configuration and data -- even though when I set up the agent job step, the data sources display the production values.  The SQL Server Agent account is a member of the administrator group on the server.  Does anyone know why the package would revert configurations like this?