A project for enum types only, is it a good idea?

I'm developing two libraries to access a SQL Server 2012 database using Entity Framework 6.1.3 Code First, C# and .NET Framework 4.0.

Now I have two projects: one with the classes that represent the tables in my database (I think these classes are called POCOs). And another one to use these classes in a SQL Server database. This last project has the DbContext, EntityTypeConfiguration and the enums that represent fixed values in database.

Now, if I want to use that enums I have to add a reference to the entire project, and I think, it is not a good idea.

I have thought to move them to the POCOs' project, but I'm not sure if this is the right place to put them.

And the last think I've thought is to move them to another project, but this can be overkilling.

What do you recommend me?